Skip to content

fix: align POSTGRES_DB in prisma docker-compose with .env.example#28638

Open
officialasishkumar wants to merge 3 commits intocalcom:mainfrom
officialasishkumar:fix/docker-compose-postgres-db-name
Open

fix: align POSTGRES_DB in prisma docker-compose with .env.example#28638
officialasishkumar wants to merge 3 commits intocalcom:mainfrom
officialasishkumar:fix/docker-compose-postgres-db-name

Conversation

@officialasishkumar
Copy link
Copy Markdown

What does this PR do?

The development docker-compose file at packages/prisma/docker-compose.yml had POSTGRES_DB set to "cal-saml", which is the SAML database name. This creates a mismatch with .env.example, which sets DATABASE_URL pointing to a database named "calendso".

When a contributor runs yarn dx with a fresh Docker volume, Docker creates a database named cal-saml, but Prisma migrations target the calendso database (from .env.example), leading to connection failures.

The root-level docker-compose.yml already correctly uses "calendso". This one-line change makes the prisma-specific docker-compose consistent with both .env.example and the root-level docker-compose.yml.

Visual Demo (For contributors especially)

N/A — configuration-only change with no UI impact.

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  1. Delete existing Docker volumes: docker compose -f packages/prisma/docker-compose.yml down -v
  2. Copy .env.example to .env (or verify DATABASE_URL points to localhost:5450/calendso)
  3. Run yarn dx to start Docker and run Prisma migrations
  4. Verify that the database calendso is created and migrations succeed without errors
  5. Confirm that psql -h localhost -p 5450 -U postgres -l shows a database named calendso (not cal-saml)

The development docker-compose file at packages/prisma/docker-compose.yml
was configured with POSTGRES_DB set to "cal-saml", which is the SAML
database name. This causes a mismatch with .env.example which specifies
DATABASE_URL pointing to a database named "calendso".

When a contributor runs `yarn dx` with a fresh Docker volume, Docker
creates a database named "cal-saml", but Prisma migrations target the
"calendso" database from .env.example, leading to connection failures
or silent inconsistencies.

The root-level docker-compose.yml already correctly uses "calendso".
This change makes the prisma-specific docker-compose consistent with
both .env.example and the root docker-compose.yml.

Fixes calcom#28635
Fixes calcom#28106
@github-actions github-actions bot added the 🐛 bug Something isn't working label Mar 28, 2026
@officialasishkumar officialasishkumar marked this pull request as ready for review March 28, 2026 20:46
@officialasishkumar officialasishkumar requested a review from a team as a code owner March 28, 2026 20:46
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Copy link
Copy Markdown
Member

@sahitya-chandra sahitya-chandra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sahitya-chandra sahitya-chandra added ready-for-e2e run-ci Approve CI to run for external contributors labels Mar 29, 2026
@romitg2 romitg2 enabled auto-merge (squash) March 30, 2026 10:44
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.

@github-actions github-actions bot added the Stale label Apr 6, 2026
@romitg2 romitg2 removed the request for review from a team April 15, 2026 14:45
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 15, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d6bde1f-01aa-4e77-a776-bae21bea0aa6

📥 Commits

Reviewing files that changed from the base of the PR and between f86e255 and ab716be.

📒 Files selected for processing (1)
  • packages/prisma/docker-compose.yml

📝 Walkthrough

Walkthrough

This pull request updates the Docker Compose configuration for the Postgres container in the Prisma package. The POSTGRES_DB environment variable is changed from "cal-saml" to "calendso". This modification updates the default database name that will be created when the Postgres container initializes. All other Docker Compose service settings, including ports, volumes, and healthcheck configuration, remain unchanged. This is a configuration-only change with no impact to application code or public exports.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: aligning the POSTGRES_DB environment variable in the prisma docker-compose file with the database name specified in .env.example.
Description check ✅ Passed The description thoroughly explains the issue, root cause, the one-line fix, and provides detailed testing steps that directly relate to the changeset.
Linked Issues check ✅ Passed The PR directly addresses both linked issues (#28635 and #28106) by changing POSTGRES_DB from 'cal-saml' to 'calendso', aligning Docker configuration with .env.example defaults and eliminating the database name mismatch that caused onboarding friction.
Out of Scope Changes check ✅ Passed All changes are in-scope; the PR modifies only the POSTGRES_DB environment variable in packages/prisma/docker-compose.yml, which directly addresses the consistency issue described in the linked issues.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐛 bug Something isn't working ready-for-e2e run-ci Approve CI to run for external contributors size/XS Stale

Projects

None yet

3 participants